forked from squidfunk/mkdocs-material
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pump @ 2024.11.05 #46
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: natakazakova <[email protected]>
…dates (squidfunk#6981) * Use Babel's `format_datetime`, not `format_date` I am using MkDocs-Material 9.5.15 and Babel 2.14.0. When setting the config value `blog.post_date_format: "yyyy-MM-dd hh:mm:ss"`, the blog plugin crashes during compilation with the error "date objects have no hour field". I believe this is occurring because the plugin provides a `datetime` to `babel.dates.format_date`, which upcasts it to a plain, timeless, `date`. Making this change to use `babel.dates.format_datetime` instead resolved the error and demonstrated expected behavior. While I recognize that it is likely uncommon for a blog to want to include sub-date timestamps in any of these fields, I believe that the current documentation, > The format string must adhere to babel's pattern syntax and should not contain whitespace implies that _any_ of Babel's pattern markers are acceptable here. I would consider > The format string must adhere to Babel's pattern syntax for calendar dates and should not contain whitespace to also be a sufficient fix for this case. ---- Thank you for your effort in creating this project; it has been a wonderful benefit to my team, and this is the first minor problem we've had in months of using it. * Make the change in src/, not material/
* fix(social): CairoSVG OSError handling in social plugin Related issue: squidfunk#6817 Co-authored-by: Guts <[email protected]> * feat(docs): Add troubleshooting guide for CairoSVG crash --------- Co-authored-by: Kamil Krzyśków <[email protected]> Co-authored-by: Guts <[email protected]> Co-authored-by: Martin Donath <[email protected]>
Unicode, case-sensitive reference setting causes error below. ``` yaml.constructor.ConstructorError: expected a mapping node, but found scalar ``` Update related sections in the documentation to address this issue. Newer Python-Markdown has `slugify_unicode` built-in, so this ```yaml markdown_extensions: - toc: slugify: !!python/name:markdown.extensions.toc.slugify_unicode ``` also works for case-insensitive use cases. Fixes: ee1e675 ("Update slug reference")
Fix typos
Co-authored-by: stcksmsh <[email protected]>
Signed-off-by: hanghuge <[email protected]>
* add missing `icon`s to theme schema https://squidfunk.github.io/mkdocs-material/setup/changing-the-logo-and-icons/?h=icons#site-icons * Add missing schema defaults
Use `config.site_name` instead of `page.title`.
* Add more Projects using Material for Mkdocs to README.md * Remove PySimpleGUI no longer open source
Minor spelling fix.
* Updated images documentation to include pymdownx.blocks.caption extension * put back HTML figure in image caption docs * fix typo in image captions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.